home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Gold Medal Software 3
/
Gold Medal Software - Volume 3 (Gold Medal) (1994).iso
/
os2
/
snpdmp.arj
/
SNAPDUMP.DOC
< prev
next >
Wrap
Text File
|
1992-05-21
|
108KB
|
2,773 lines
IBM SNAPDUMP/2
Data Collector and
Formatter
C. W. (Bill) Rogers
Austin, Texas
May 22, 1991
────────────────────────────────────────────────────────────────────────────
Introduction
SnapDump is a set of tools which assists with problem determination
in the OS/2 environment. SnapDump provides the ability to capture
a wide variety of system data into a single, easily transportable file.
The collection of data is controlled by the contents of a tailorable
flat ASCII file. Although a sample version of this file is shipped
with SnapDump (SNAPDUMP.DAT), this ASCII file can be easily modified
by support personnel to customize the collection of data.
In addition, SnapDump provides an easy-to-use menu interface for
displaying the contents of the output file that contains the
system data collected by SnapDump.
Data Collection
SnapDump includes a program (SNAPDUMP.EXE) that provides the ability
to collect many types of data. The data collected falls into four
categories:
* Files (binary and ASCII)
* Data areas contained in named shared segments
* Standard output and standard error from programs invoked by SnapDump
* Environmental information automatically collected by the
SnapDump data collection program.
* The system trace buffer (if the system trace is active)
Formatting the Data
SnapDump includes a program (SNAPDF.EXE) which provides a PM interface
useful for viewing and formatting the contents of a file that contains
the data collected by SnapDump.
The formatting program provides three views of the data:
* Hexadecimal plus ASCII
* Hexadecimal plus EBCDIC
* ASCII only
The view of the data is toggled with the PF12 key.
The SnapDump formatter can also be used to extract data from the
SnapDump output file, returning it to its original binary format.
This is particularly useful for binary files that require specialized
tools or programs to view them in a meaningful way (for example, the
Communications Manager configuration file).
Utilities
A set of utility programs are provided with SnapDump, to assist in
the collection of data helpful when performing problem determination.
QMC.EXE Provides hardware specific information
FINDSEG.EXE Displays segment information
NETSESS2.EXE Local LAN session information
DIRSTAT.EXE Exhibits adapter information
NCBSTAT.EXE Displays Netbios information
TRADUMP.EXE Shared Ram dump from Token-Ring
LAPSDUMP.EXE LAPS information (to be included by 6/1/92)
See SnapDump Utility Prgrams on page 12 for more information on
the utilities.
─────────────────────────────────────────────────────────────────────────────
Operating Environment
There are no special requirements, other than OS/2. SnapDump will
operate in the following environments:
* SE 1.2 through SE 2.0
* EE 1.2 through EE 1.30.2
* SE 1.30.1 (including Extended Services)
* SE 1.30.2 (including Extended Services and LAN Server 2.0)
─────────────────────────────────────────────────────────────────────────────
The SnapDump Package
SnapDump consists of the following files:
SNAPDUMP.EXE The data collection program
SNAPDF.EXE The data formatter program
SNAPDUMP.DAT Sample ASCII input file for the collection program
SNAPDUMP.INF On-line documentation for SnapDump
SNPNL001.HLP Help file for SnapDump
QMC.EXE Qsystem program to display hardware information
FINDSEG.EXE Program to display segment information
NETSESS2.EXE Local LAN session statistical and status
DIRSTAT.EXE 802.2 adapter level information
NCBSTAT.EXE Netbios status information
TRADUMP.EXE Shared Ram dump from Token-Ring
TRADUMP.SYS Driver for Shared Ram dump
LAPSDUMP.EXE LAPS information (this included before 6/1/92)
─────────────────────────────────────────────────────────────────────────────
Installing SnapDump
These installation instructions assume that you are familiar with using
the OS/2 full screen session command line and that you wish to create a
separate directory on the C drive for SnapDump. You may substitute a
different drive letter and directory name and/or omit steps where
appropriate.
* Download the SNAPDRIV EXEBIN file.
* Install with either:
- Create a directory for SNAPDUMP (e.g. 'mkdir SNAPDUMP').
- Execute the following: 'SNAPDRIV -d -o C:\XXXXXXXX',
this will place executable into directory 'XXXXXXXX'.
* Or
- As an option, place SNAPDUMP in directory OS2\SYSTEM.
- Execute the following: 'SNAPDRIV -d -o c:\OS2\SYSTEM'.
this will place executable into directory 'OS2\SYSTEM'.
─────────────────────────────────────────────────────────────────────────────
Collecting Data with SnapDump
The SnapDump data collection program (SNAPDUMP.EXE)
utilizes a flat ASCII file as input. This file contains the
instructions that specify what data is to be collected (e.g. files,
memory areas), and what data gathering programs are to be invoked.
This flat file approach makes data collection with SnapDump very
flexible in that it can be easily tailored to add or remove
items to be collected. When run, SnapDump will produce a single
output file that contains all collected data.
SnapDump is invoked from the command line. There are three forms
of the command:
SNAPDUMP
This form of the command assumes that the input file, snapdump.dat,
exists, and that it contains a list of files, data and programs to
be processed by SnapDump. The output file defaults to, snapdump.dmp.
SNAPDUMP {input-fname}
The {input-fname} parameter is the name of the flat ASCII file that
contains the list of items to be captured. The output file defaults
to snapdump.dmp.
SNAPDUMP {input-fname dump-fname}
The {input-fname} parameter is the name of the
flat ASCII file that contains the list of items to be captured.
The {dump-fname} parameter is the name of the file into which
SnapDump will write all the captured data. In this document,
it is also called the SnapDump output file.
SnapDump Input File
The SnapDump input file controls the information to be captured in
the SnapDump output file. The SnapDump input file may be edited with
any ASCII editor, including the OS/2 system editor. The following
describes the types of information that can be captured and how it
is to be specified in the flat file.
* A 'f/' in column 1 indicates that a file is to be captured.
For example:
f/config.sys
When a file is captured, the contents of the file are appended to
the SnapDump output file. Wildcards may be specified, but be
aware that the SnapDump output file may become very large
if the wildcard specification is too broad. Note that files
that are "in-use", such as the Communications Manager
'MESSAGE.DAT' and 'ERROR.DAT' files are collected by SnapDump.
* A 'p/' in column 1 indicates that the specified program is to
be invoked. For example:
p/c:\qmc.exe -d
Any programs (including .CMD files) that can be run from the
OS/2 command prompt and that write to standard output and/or
standard error may be specified. The standard output and/or
standard error output of the program is appended to the
SnapDump output file. The output of programs that use other
techniques of writing to the screen, such as Presentation
Manager "Win" calls or "VIO" calls, cannot be captured by
SnapDump.
* A 'm/' in column 1 indicates that a named shared memory
segment ("\SHAREMEM\...") is to be captured. For example:
m/\SHAREMEM\ACS\RAS_SEG
The contents of the named shared segment are appended to the
SnapDump output file. Wildcards for named shared memory are
not allowed. Certain named shared memory segments are protected
and cannot be dumped. The names of the named shared memory files
in the system may be obtained by issuing the following
command at the command prompt:
pstat /m
* Any other value in column one causes the line to be treated
as a comment.
If the system trace is active, the system trace buffer is automatically
captured by SnapDump and appended to the SnapDump output file.
Searching for Files
When SnapDump scans for files, it will search all accessible drives,
including shared drives on servers and diskette drives. Multiple
instances of a file will be collected, if they exist.
Sample SnapDump Input File
The following SnapDump input file is shipped with SnapDump, and can
be modified as required:
*This is a sample file to show SNAPDUMP/2 Capability. Most
*of the entries have been deactivated (* in first column) to
*reduce size of the output file.
*File names and paths will differ with OS/2 release level.
*The user may customize as needed.
*
* OS/2 information
*
f/config.*
f/syslevel.*
f/startup.cmd
f/*.ini
*f/os20001.dat
*f/log0001.dat
*
* FFST/2 files
*
*f/epw.ini
*f/snapdump.dat
*f/os2mlog.dat
*p/dir c:\os2\system\*.dmp
*
* Communication Manager
*
*p/display.exe
*f/*.cfg
*f/*.ndf
*f/*.sec
*f/*.cf2
*f/error.dat
*f/message.dat
*f/esinst.hst
*f/acs.pro
f/acslan.log
f/lantran.log
*f/c2instal.log
*f/install.log
*f/message.log
*f/custbld.hst
*f/cmfeater.dat
*m/\sharemem\acs\ras_seg
*
* Database Manager
*
*f/sqldbdir
*f/sqlsystm
*f/sqldbcon
*f/sqluif.*
*f/sqlnodir
*f/sqlgwdir
*f/sqlogctl.lfh
*f/dbdrqlib.cfg
*
* LAN Server 2.0
*
*f/net.err
p/net error
*f/net.acc
*f/net.aud
*
* LAN status command
*
*p/net statistics requester
*p/net statistics server
*p/net config requester
*p/net config server
*p/net files
*p/net sessions
*p/net share
*p/net status
*p/net view
*p/net who
*
* Workstation Status Programs
*
*p/netsess2.exe
*p/ncbstat.exe *
p/dirstat.exe
*p/findseg -S C:\
p/qmc.exe -d
p/pstat.exe
*
*Adapter Shared Ram Dump for OS/2 Extended Edition
*Version 1.3 (device driver TRADUMP.SYS required)
*
*p/tradump /f
*
*Adapter Shared Ram and Netbios Dump for OS/2 version 2.0
*with LAPS (Lan Adapter and Protocol Support)
*
*p/lapsdump /f (will be provided by 5/1/92)
*
─────────────────────────────────────────────────────────────────────────────
Formatting Data Collected with SnapDump
The SnapDump Format Utility provides an easy to use menu interface
to select and display the contents of the SnapDump output file.
Because each data item collected in the dump file is tagged with an
"entry title", it is very easy to select a specific data item for
display. It is not necessary to display the entire dump file.
In addition, the SnapDump Format Utility can be used to extract
a specified data item, returning it to its original binary format.
This is particular useful for binary files that require specialized
formatters. The binary file can be extracted from the dump file
and stored as an individual file in its original binary format.
The SnapDump Format utility can be accessed directly from
the command line by entering the following command:
SNAPDF {dump-fname}
The {dump-fname} parameter is the name of the dump file containing
data previously captured with an invocation of SNAPDUMP.
If the {dump-fname} parameter is supplied, or 'snapdump.dmp' exists,
the 'Dump Formatter' window will be displayed.
If no dump file name is specified and a file named 'snapdump.dmp'
does not exist, the following standard file 'Open' dialog box will
appear to assist the user in selecting a dump file name.
The file 'open' dialog will appear as follows:
┌──┬───────────────────────────────────────────────────────────┐
│==│ OPEN │
├──┴───────────────────────────────────────────────────────────┤
│ │
│ ┌───────────┬──────────────────────────────────────┐ │
│ │File name: │ *.dmp │ │
│ └───────────┴──────────────────────────────────────┘ │
│ │
│ ┌──────────────┬──────────────────────────────┐ │
│ │Directory is: │ C:\SNAPDUMP\ │ │
│ └──────────────┴──────────────────────────────┘ │
│ ┌──────────────┐ ┌──────────────┐ │
│ │ Files: │ │ Directories: │ │
│ └──────────────┘ └──────────────┘ │
│ ┌────────────────────┬──┐ ┌────────────────────┬──┐ │
│ │ SNAPDUMP.DMP │ │ │ .. │ │ │
│ │ ├──┤ │ [A:] ├──┤ │
│ │ │ │ │ [C:] │ │ │
│ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │
│ ├──┬─────────────────┼──┤ ├──┬─────────────────┼──┤ │
│ │<-│ │->│ │ │ │ │ │
│ └──┴─────────────────┴──┘ └──┴─────────────────┴──┘ │
│ │
│ ┌────────┐ ┌────────┐ ┌────────┐ │
│ │ Open │ │ Cancel │ │ Help │ │
│ └────────┘ └────────┘ └────────┘ │
│ │
└──────────────────────────────────────────────────────────────┘
The Tab and Shift+Tab keys, as well as the mouse, may
be used to move between controls in the dialog box. The Left Arrow
and Right Arrow keys may be used to move between the 'Open', 'Cancel',
and 'Help' buttons. The user may press the F1 key, or click on the
'Help' button to obtain context-sensitive help on the current
(focus) control of the dialog box. The 'Directory is:' field is
read-only; it allows the user to see long subdirectory names.
Only files identified as SnapDump or First Failure Support Technology/2
(FFST/2) dump files will appear in the 'Files:' listbox. The user may
enter any file name in the 'File Name:' entry field. The dump
formatter will ensure the file is a SnapDump or FFST/2 dump file.
Once a dump file and the 'Open' button are selected: the
'Dump Formatter' window will display the formatted SnapDump
data as well as a list of the data items captured by Snapdump.
SnapDump Dump Format on page 10 illustrates what this display
may look like ('after maximizing the window'):
┌──┬────────────────────────────────────────────────────────────────┬───┬───┐
│==│ Dump Formatter │ │ │
├──┴────────────────────────────────────────────────────────────────┴───┴───┤
│ File Options Help │
├───────────────────────────────────────────────────────────────────────────┤
│ SNAPDUMP.DMP [1] │
│ ┌───────────────────────────────────────────────────────────────┬───┐ │
│ │IBM SNAPDUMP/2 [2] │ V │ │
│ └───────────────────────────────────────────────────────────────┴───┘ │
│ │
│ [3] 09-04-1991 16:10:36.75 SNAPDUMP │
│ │
│ ┌───────────────────────────────────────────────────────────────┬───┐ │
│ │Process Environment [4] [5]│ V │ │
│ └───────────────────────────────────────────────────────────────┴───┘ │
│ │
├───────────────────────────────────────────────────────────────────────────┤
│ │
├─────────────────────────────────────────────────────────────────────────┬─┤
│COMSPEC=C:\OS2\CMD.EXE │ │
│PATH=C:\OS2;C:\MUGLIB;C:\OS2\SYSTEM;C:\CMLIB;C:\CMLIB\APPN;C:\OS2\INSTALL├─┤
│DPATH=C:\OS2;C:\MUGLIB\DLL;C:\CMLIB;C:\CMLIB\APPN;C:\OS2\SYSTEM;C:\OS2\IN│ │
│PROMPT=$i[$p] │ │
│KEYS=ON [6] │ │
│BOOKSHELF=C:\OS2\BOOK; │ │
│HELP=C:\OS2\HELP; │ │
│ │ │
│C:\snapdump\SNAPDUMP.EXE │ │
│snapdump │ │
│ snapdump.dat │ │
│ │ │
│ │ │
│ │ │
│ │ │
│ ├─┤
│ │ │
└─────────────────────────────────────────────────────────────────────────┴─┘
Initial SnapDump Format Screen
The SnapDump Dump Formatter screen needs to be maximized to
view all the data.
The first field in the window (see [1]) is the dump
file currently being displayed (for example: SNAPDUMP.DMP).
The second field in the window (see [2]) contains a unique
dump segment identifier. If the SnapDump file contains a
large number of data entries (where a data entry represents
a capture file, output from a program, or a shared segment),
the dump file will be segmented. Each segment is identified
in this field, which can be scrolled by using the down-arrow
on the right. Use the down-arrow at the right of this
field to see the complete list of segments, and to select the
desired segment. Segmentation only occurs after approximately
300 data entries are collected.
The third field in the window (see [3]) is the date and time of
the dump as well as an the identifier of the of the program
that created the dump file (in this case, the originator is "SNAPDUMP").
The fourth field in the window (see [4]) contains the currently
selected data item. When the Dump Formatter window is initially
displayed, 'Process Environment' is pre-selected and is displayed
in [6]. The environment information collected by SnapDump includes
'PATH:', 'DPATH:', etc..
The down arrow button (see [5]) can be clicked-on (or press [Enter:])
to get a complete list of data items captured in the SnapDump output
file. See SnapDump Dump Format on page 10 for an example of a list of
data items. [7] in SnapDump Dump Format on page 10 represents the
list of data items.
When the Dump Formatter window is first displayed, the sixth
field in the window (see [6]) contains an ASCII representation
of the 'Process Environment'. The data can be displayed in
three formats:
* Hexadecimal plus ASCII
* Hexadecimal plus EBCDIC
* ASCII only
PF12 is used to change views of the data.
┌──┬────────────────────────────────────────────────────────────────────┬──┬──┐
│==│ Dump Formatter │ │ │
├──┴────────────────────────────────────────────────────────────────────┴──┴──┤
│ File Options Help │
├─────────────────────────────────────────────────────────────────────────────┤
│ SNAPDUMP.DMP [1] │
│ ┌──────────────────────────────────────────────────────────────────┬──┐ │
│ │IBM SNAPDUMP/2 [2] │V │ │
│ └──────────────────────────────────────────────────────────────────┴──┘ │
│ │
│ [3] 09-04-1991 16:10:36.75 SNAPDUMP │
│ │
│ ┌──────────────────────────────────────────────────────────────────┬──┐ │
│ │Process Environment [4] [5]│V │ │
│ └──────────────────────────────────────────────────────────────────┴──┘ │
│ │
├─────────────────────────────────────────────────────────────────────────┬───┤
│ │ V │
├─────────────────────────────────────────────────────────────────────────┼───┤
│Process Environment │ │
│C:\CONFIG.SYS │ │
│C:\OS2\INSTALL\CONFIG.SYS │ │
│C:\CMLIB\SYSLEVEL.ACS │ │
│C:\OS2\SYSLEVEL.EPW [7] │ │
│C:\MUGLIB\SYSLEVEL.MUG │ │
│\SHAREMEM\ACS\RAS_SEG │ │
│'NET STATISTICS REQUESTER' │ │
│'PSTAT.EXE' │ │
│'QMC.EXE │ │
│C:\OS2\EPW.INI │ │
│ │ │
│ ├───┤
│ │ A │
└─────────────────────────────────────────────────────────────────────────┴───┘
SnapDump Dump Format screen after dump file name selected
In this example, the portion of the window with the list of collected
data items (see [7]) is used to select a data item for display.
To select an item for display, single click on the data item and then
press 'Enter:' (or then double click on the item in [4]).
The data can be displayed in three formats:
* Hexadecimal plus ASCII
* Hexadecimal plus EBCDIC
* ASCII only
PF12 is used to change views of the data.
The F4 key may be used to toggle the visibility of the list box
part of the prompted entry fields whenever the entry field (see
[4]) has the keyboard focus keyboard focus (clicking on the
down-arrow button (see [5]) is the equivalent). To actually
select an item from the dump list or the entry list, use the
up- and down-arrow keys (or the mouse if the list box control
of the upper entry area is visible) and then either press Enter
or double-click on the entry field portion of [4] to complete the
selection. If a new entry is selected, it will be formatted
and displayed.
Items in the list that are in quotes (for example, 'PSTAT.EXE', see
[7]) represent programs that were invoked by SnapDump. Output
from these programs is selected for viewing in the same manner as files.
Files that were captured in a SnapDump output file may be copied to
disk with the 'SAVE AS...' found under 'FILE:' from the action bar.
Select the data item, go to the action bar and select 'FILE:',
then select 'SAVE AS'. On the 'SAVE AS' dialog box
set 'Select output type' to binary data and double click on
'SAVE'. For example, files such as OS2.INI should be saved
as binary data to preserve their binary format.
The captured file will then be written to disk. This function will
not write OS/2 Extended Attributes.
A new SnapDump output file can be opened by selecting 'Open' found
under 'FILE' from the action bar. This is useful when multiple
SnapDump output files are to be viewed.
─────────────────────────────────────────────────────────────────────────────
Transporting SnapDump Output Files
If the SnapDump output file is too large to fit on a single diskette
(even after packing it), the 'Backup' function provided with OS/2
can be used to store a very large file on multiple diskettes.
Conversely, the 'Restore' function provided with OS/2 can be used to
restore the diskette-spanning information into a single file.
The SnapDump output file can be sent to a central support location
for diagnostic assistance. When using the file transfer capabilities
of OS/2 Communications Manager to send the output file to a host,
insure the that the record format and characteristics of the host
computer file is set to 'variable'.
* If you are using the OS/2 command line to enter the SEND
command for file transfer, use the RECFM V option. For example:
send c:output.dmp a:output dump a (recfm v
* If you are using OS/2 Communications Manager File Transfer
Profiles to send the output file; (1) under 'Modify host
file characteristics options', select - Yes; (2) under
'Record format of host file', select - Variable.
─────────────────────────────────────────────────────────────────────────────
Support for SnapDump
Usage Support
Usage support, for Customers and SEs, will be provided through
EQUAL/ASKQ. Keyword for entries should be "SNAPDUMP".
Defect Support
Defect support for SnapDump will be handled through SNAPDUMP FORUM
on IBMPC which will be monitored. Defect will be answered with in 2
weeks.
─────────────────────────────────────────────────────────────────────────────
SnapDump Utility Programs
Any programs that provide useful problem determination information,
or status, are candidates for use with SnapDump. The following
programs may be of use to you, and are installed with SnapDump:
QMC.EXE Displays hardware information
FINDSEG.EXE Displays segments
NETSESS2.EXE Displays session statistical and status
DIRSTAT.EXE Exhibits adapter information
NCBSTAT.EXE Displays Netbios information
The following program is provided with Extended Services for OS/2.
To install this program, you must install the Communications Manager
Utilities found on the Additional Features panel during initial
installation (ESINST) or re-install (REINST). See the Extended
Services Communications Manager Command Reference for more information
about using this program.
DISPLAY.EXE Displays the active SNA configuration
The following program is provided with the base operating system.
PSTAT.EXE Displays system information
QMC
The QMC program returns a wealth of useful information about the
the hardware installed on the machine on which it is run.
You must have the IOPL=YES in your CONFIG.SYS for QMC to function.
The following options are available when invoking QMC:
Options
-------
-? or ? lists options (help)
-A list all supported Microchannel adapters supported by QMC
(can be used with the -O option to redirect to file)
-D list more detailed QMC information
includes : adapter configuration for Microchannel
model, submodel
fixed disk sectors/heads/cylinders.
-O redirect output to QSYSTEM.OUT
-Ofilename redirect output to file
For example:
QMC -Ops2data.fil
would redirect the output of QCONFIG to ps2data.fil.
key=value define key with value for machine information output
There is a limit of 10 keys.
For example:
QMC User="Jeff Muir" "Location Site"=Boca
Output would include:
User : Jeff Muir
Location Site : Boca
There are a couple of methods to handle data scrolling off the screen:
QMC | MORE (pipes information from QMC into the MORE command)
QMC -O (re-directs the output to QSYSTEM.DAT)
The first technique is good if you just want to view the info
one screen at a time. The second technique works best for
keeping a permanent copy and being able to browse/edit the results.
Findseg
This program searches for the specified segments within executable
files. This version of Findseg operates only on 16-bit OS/2
operating systems.
The key word for this search is the length of a segment. There
are two basic forms of the findseg command:
Usage: findseg [switch] [drive:][path]
Usage: findseg [switch] [UNC name]
switch:
1.Segment type
-c : Report code segments only.
-d : Report data segments only.
-b : Report code and data segments (default).
2.Segment length
-l : The string after this switch is the length of the target
segment. If the length is specified as HEX format, it must
start with X (or x). Spaces aren't allowed between -l and
the string. If the string is 0 (or x0) the length is 65536.
If this switch isn't set, all segments will be reported.
-r : Report the segments whose length are between LENGTH - DELTA
and LENGTH + DELTA. (LENGTH is the specified length by -l
and DELTA is the specified length by this switch.)
Default is -r1.
3.File type
-E : Search EXE files only.
-D : Search DLL files only.
-S : Search SYS files only.
-B : Search EXE and DLL files.
One or more switches may be set. The default is -E -D -S.
4.Access rights byte
-A : The string after this switch is the access right byte of
the target segment. If it is specified as HEX format, it must
start with X (or x). Spaces aren't allowed between -A and
the string. PRESENT, ACCESSED and EXPANSION DIRECTION (data
segment) bits will not be tested. This access rights byte is
displayed as **ACC=?? in the TRAP-D popup panel.
(**:CS, DS, SS, ES, ER, ??:Access rights byte)
5.Disassemble
-I : Output disassembled code. The string after this switch is the
IP value. If it is specified as HEX format, it must start with
X (or x). Spaces aren't allowed between -I and the string.
This switch is valid for CODE segments. In the disassembled
code, the relocation information is not resolved.
resolved.
6.Miscellaneous
-p : Pause after a screen is full. This switch is ignored when
OUTPUT is redirected to a file.
-s : Search from sub-directories.
drive : Drive name. Default is the current drive.
path : Path name. Default is the current path.
UNC name : Universal naming convention name. \\server name\net work
name[\path]
Example: findseg -lx6000 -rx1000 -s -D -Ix400 C:\
This searches DLL files from a root and its all sub-directories in
drive C. And it reports file names and length and attribute of
segments whose size are between 0x5000 and 0x7000 bytes.
They are output in the following format.
Search path : C:\ and its sub-directories
Search file : *.DLL
Search range : 0x05000(20480)-0x07000(28672) bytes
Access rights: not specified
C:\MYDLL\TEST.DLL
12610bytes 90-05-10 15:25:00
004 05200 DATA FIXED NONSHARED PRELOAD R-O NORELOC PL3 DISCARDABLE
C:\OS2\DLL\PMGPI.DLL
265110bytes 90-03-30 01:20:00
002 05FCC CODE MOVABLE NONSHARED LOADONCALL E/R RELOC PL2 NONDISCARDABLE
Instruction: push es:[bx+si]
C:\OS2\DLL\OS2SM.DLL
64512bytes 90-03-30 01:20:00
001 05789 CODE MOVABLE NONSHARED PRELOAD E/R RELOC PL3 NONDISCARDABLE
IP is invalid value.
C:\OS2\DLL\DISPLAY.DLL
342016bytes 90-03-30 01:20:00
002 067DE CODE MOVABLE SHARED PRELOAD E/R RELOC PL2 NONDISCARDABLE
IP is invalid value.
00A 050BE DATA MOVABLE SHARED PRELOAD R/W NORELOC PL2 NONDISCARDABLE
5 segments in 4 files
Note : The meaning of each value is as follows:
C:\OS2\DLL\PMGPI.DLL <--- File name
265110bytes 90-03-30 01:20:00 <--- File size and update time
001 05FCC CODE MOVABLE NONSHARED LOADONCALL E/R RELOC PL2 NONDISCARDABLE
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
Instruction: push es:[bx+si] <-- Disassembled code at IP=0x400
(1) : Entry id in segment table
(2) : Minimum allocation size for the segment
(3) : Segment type (CODE/DATA)
(4) : Fixed or Movable segment
(5) : Shared or Nonshared segment
(6) : Preload or Load on call segment
(7) : Execute/read or Execute-only if code,
Read/Write or Read-only if data
(8) : Relocation table present or not
(9) : Privilege level
(10): Discardable or Nondiscardable segment
3. Hints to determine TRAP-D module
To find the TRAP-D module, set the CSLIM value found in the TRAP-D
panel to segment length (-l switch), instead of DSLIM, ESLIM or SSLIM
since the data segments (DS, ES and SS) may have been allocated or
reallocated after the process started.
process started.
You had better set IP value(by -I switch). When two or more modules are found,
you can determine TRAP-D module from disassembled code. For example, TRAP-D
may not occur on the following instructions
mov ax, 0
inc cx
:
etc.
and the following instructions have potential of TRAP-D (or TRAP-C).
TRAP-D occurs on the following condition.
pop ax <--- sp exceeds SSLIM (In this case TRAP-C
will occur).
les bx, es:[bx+si] <--- bx+si exceeds ESLIM or ES is invalid
rep movs <--- si exceeds DSLIM or di exceeds ESLIM
:
etc.
NETSESS2 program operation
The NETSESS2 program obtains and prints session statistics which
are kept by the LAN adapter card (or NETBEUI in the case of the
Token Ring). The session statistics may be obtained for the
local station only.
The syntax of the NETSESS2 command line is as follows:
netsess2 [-<lana>] [<session_name>]
The optional flag -<lana> indicates use of the alternative LAN adapter
specified instead of the default which is LAN adapter 0. Possible
values for <lana> are 1, 2, and 3.
If the optional <session_name> is specified, only the statistics for
sessions with that local name will be printed. Otherwise statistics
for all sessions will be printed.
The session statistics printed appear as follows:
Session statistics for local station
Number of Sessions in progress = 03
LSN Status Local Name Remote Name Rcv Send
--- ------- ---------------- ---------------- --- ----
003 Session morbius YKTLAN1 001 000
004 Session jeffat robbi 001 001
005 Session morbius altair 001 000
Receive Datagram commands outstanding 000
Receive Any commands outstanding 004
The column labeled 'LSN' contains the Local Session Numbers which
are assigned to each session by the LAN adapter.
The column labeled 'Status' contains keywords indicating the
status of the session. See the Tech. Ref. Manual for explanations
of these status conditions.
The column labeled 'Local Name' contains the LAN adapter name
used at the local adapter in the CALL or LISTEN command that
established the session.
The column labeled 'Remote Name' contains the LAN adapter name
used at the remote adapter in the CALL or LISTEN command that
established the session.
The column labeled 'Rcv' contains the number of outstanding
RECEIVE commands for this session.
The column labeled 'Send' contains the number of outstanding
SEND commands for this session.
The two lines following the tabular information contain the
number of outstanding RECEIVE DATAGRAM commands, and the number
of outstanding RECEIVE ANY commands, respectively.
INTRODUCTION TO INSTALLING AND USING
TOKEN-RING NETWORK ADAPTER SHARED RAM DUMP (TRADUMP)
February 10, 1992
Mark B. Arslan (ARSLAN @ RALYDPD)
Distributed Systems Management Technical Support
Networking & Systems Services & Support
Research Triangle Park, NC
PREFACE
In the complex area of distributed OS/2 local area networks, one of the
most important elements of problem management is problem source
identification. It is the process of isolating a problem to its failing
component or the system resource responsible for the problem. Problem
source identification (or PSI) is particularly difficult in this
environment due to the large number of interrelated system components
and the relative scarcity of adequate PSI facilities (tools, utilities,
product functions) and documented PSI procedures.
A class of LAN problems that can be especially challenging is that of
LAN connectivity ("System A can't communicate with System B over the
network"). Solving this type of problem often requires knowledge of the
workings of the layers of the protocol stack (802.5, 802.2, NetBIOS,
SNA, etc.) on each system, including APIs, resource requirements,
contents of internal buffers, event logs, messages, and formats and
protocols of frame exchange. When connectivity problems occur, clues
are often left behind. Analyzing these elements of the protocol layers
will usually lead to the solution of the problem, provided that the
problem-solver has adequate tools and sufficient skills.
One particularly useful component for PSI is the shared RAM in the IBM
PS/2 Token-Ring Network adapter, an area of adapter memory (up to 64K
bytes) containing buffers for the 802.5 and 802.2 layers of the protocol
stack. There is a tool called TRADUMP that dumps this buffer area and
formats the dump data into an ASCII text file or STDOUT. The purpose of
this manual is to introduce technically-knowledgeable SEs and
specialists to using TRADUMP (in conjunction with other tools and
facilities) to aid in the resolution of LAN connectivity problems.
As of this writing, TRADUMP has been tested on OS/2 Extended Edition
V1.3 only. This document discusses the implementation of shared RAM and
TRADUMP for OS/2 Extended Edition V1.3. LAN Adapter and Protocol
Support (LAPS) under OS/2 Extended Services V1.0 and OS/2 LAN Server
V2.0 handles shared RAM and the NetBIOS/802.2 interface quite
differently than V1.3. It is a well-understood and accepted requirement
that TRADUMP be enhanced to work under LAPS, as well.
Related Publications:
A much more detailed discussion of interpreting TRADUMP output can be
found in:
Guidelines for Using Token-Ring Network Adapter Shared RAM Dump
(TRADUMP) for Debugging LAN Connectivity Problems
No form number has been assigned yet, but a copy may be obtained by
having your Systems Engineer contact this author (ARSLAN @ RALYDPD).
The following publications contain information that may also be helpful:
IBM Local Area Network Technical Reference, SC30-3383-03.
IBM Token-Ring Network Architecture Reference, SC30-3374-02.
Token-Ring Network Introduction and Planning Guide, GA27-3677.
INSTALLING TRADUMP
TRADUMP consists of two modules:
TRADUMP.SYS
A device driver that determines the location of MMIO and shared RAM in
the PS/2 memory address space, reads the contents of each, and writes
the output to a program buffer.
TRADUMP.EXE
A program that calls TRADUMP.SYS, formats the raw data from its program
buffer, and writes the formatted dump to STDOUT (i.e., text mode
standard output to the PS/2 screen).
To install TRADUMP, perform the following steps:
1. Copy both TRADUMP.SYS and TRADUMP.EXE to the local fixed disk. A
recommended approach is to copy TRADUMP.EXE into a directory that is
pointed to by the PATH statement in CONFIG.SYS. (Another alternative is
to put TRADUMP.EXE on a diskette or redirected drive. TRADUMP.SYS must
be on a local disk, since it is a device driver.)
2. Add a statement to CONFIG.SYS to load the TRADUMP.SYS device driver
at IPL time:
DEVICE=d:\path\TRADUMP.SYS
3. Re-IPL the system to allow this change to CONFIG.SYS to take effect.
RUNNING TRADUMP
TRADUMP can be run by issuing the TRADUMP command at an OS/2 command
prompt. This command requires no additional user interaction, and
writes to STDOUT, so it can be entered manually by an operator, called
by another program (e.g., SnapDump/2), or issued remotely from a product
like LAN Management Utilities/2 (LMU/2) or Distributed Console Access
Facility (DCAF).
COMMAND FORMAT
The format of the TRADUMP command is as follows:
──────┬──────────┬───┬──────────┬──── TRADUMP ─────>
└──drive───┘ └──path────┘
───┬─────────────────────────────────────┬───────┤
├───────────────── ? ─────────────────┤
│ ┌─────────────────────────┐ │
└─────V───┬─────────────────┬───┴─────┘
├─── /f<m,s> ─────┤
├─── /a<0|1> ─────┤
├───── /d ────────┤
└─────────────────┘
TRADUMP works in conjunction with device driver TRADUMP.SYS
to dump and/or format the contents of the token ring
adapter memory.
/fm format the MMIO region at 0x1E00(256) and 0x1F00(512).
/fs format control blocks from the SRAM memory.
/f or /fms format both areas indicated above.
/a specifies primary (0) or secondary (1) adapter.
/d dump the complete SRAM memory to STDOUT.
To display this format diagram, key "TRADUMP ?".
OPTIONS
TRADUMP can dump MMIO, shared RAM, or both. To dump only MMIO, key
"TRADUMP /fm". To dump only shared RAM, key "TRADUMP /fs". To dump
both MMIO and shared RAM, key "TRADUMP /fms", "TRADUMP /fsm", "TRADUMP
/f", or just plain "TRADUMP".
TRADUMP can dump either the primary or alternate Token-Ring Network
adapter. To dump the alternate adapter's shared RAM, key "TRADUMP /fs
/a1". The primary adapter is the default, and it is not necessary to
code "/a0", although it is permitted.
The "/d" parameter will create a minimally-formatted hexadecimal dump of
the entire contents of shared RAM and MMIO. This will present the data
in the transmit and receive buffers (although the boundaries between the
various buffers and control blocks are not shown, making it difficult to
interpret). This option was intended for use by IBM support personnel.
The options (/f, /a, and /d) and the values (m and s) can be entered in
either upper or lower case. The value must immediately follow the
option, with no blank separating them. If multiple options are entered,
such as "TRADUMP /fm /a1", a blank must separate the first option-value
from the second. "TRADUMP /fm/a1" will result in an error.
Since TRADUMP.EXE writes to STDOUT, the dump will scroll up the PS/2
screen. While this is necessary for use in certain products like
SnapDump/2, a more desirable approach may be to redirect STDOUT to
either a printer or a disk file:
TRADUMP >lpt1:
or
TRADUMP >g:\dumps\srammmio.dmp
The resulting ASCII text file may then be shipped to a central site for
analysis, where it can be viewed with a standard text editor by
technical support personnel.
ERRORS
If TRADUMP detects an error that prevents it from dumping Token-Ring
Network adapter memory correctly, one of the following returns code will
be displayed:
3
TRADUMP.SYS issued a programmed I/O (PIO) read to the port for the
indicated adapter, and invalid information was returned. Check that the
adapter specification on the TRADUMP command is correct (/a0 or default
for the primary adapter, /a1 for the alternate adapter), and that the
particular adapter is actually installed and configured.
4
The specified adapter is not one that is understood by this program.
Check that the adapter being dumped is one of the following:
IBM Token-Ring Network Adapter for the PC I/O Bus
IBM Token-Ring Network Adapter for the Micro Channel
5
The specified adapter indicates that it uses a paging method that is not
understood by this program.
For RC= 4 or 5, the MMIO area of the adapter memory is automatically
dumped for analysis. Have this information available when reporting
this as a problem.
A return code of 0 indicates successful completion of the dump.
PERFORMANCE
TRADUMP was designed to run on an active system without interrupting
normal operations. TRADUMP.SYS will extract the MMIO and shared RAM
information from the adapter in a split-second, and write the data to a
program buffer. Once this is done, the adapter is not "touched"
anymore. TRADUMP.EXE will then format the data and write it to STDOUT
(i.e., the screen), which could be redirected to a disk file.
On a PS/2 Model 65SX, this whole operation takes less than three seconds
(most of that time loading TRADUMP.EXE from disk, and then writing the
redirected dump back to disk).
Dumping with the "/d" option (unformatted contents of the complete
shared RAM area) takes considerably longer (1 minute, 15 seconds on a
PS/2 Model 65SX). Almost all of that time is spent writing to the disk
file. However, this option is not expected to be used very often.
SCENARIOS
What kinds of problems can TRADUMP be applied to in order to help
identify the problem source? And how can it be used most effectively?
These questions can perhaps best be answered by describing some ways in
which shared RAM and MMIO dumps have been used by IBM support center
personnel to solve customer problems with LAN connectivity.
CONFIGURATION ERRORS
OS/2 provides the capability of running many LAN applications
concurrently. To do this, the system needs to be configured properly.
Some of these configuration parameters include LAN resources, "pointers"
to other systems (e.g., partner LU definitions, gateway addresses,
server names), and various performance options. The more LAN
applications that are installed on a single system, the more likely a
configuration error is likely to occur, since many of these parameters
are interdependent.
Configuration errors can be hard to track down. With the complexity of
application programs, operating system components, and protocol layers
between the user and the actual cause of the error, it isn't uncommon
for the error message to be less than helpful in resolving the problem.
Sometimes the listings of configuration files provided to the help desk
are either out-of-date, or are of the wrong files. A common example of
this is the Communications Manager .CFG file, where the TRNETDD.SYS and
NETBDD.SYS drivers are pointing to a different file than the one that is
active for the Communications Manager configuration process. By showing
how the Token-Ring Network adapter was ACTUALLY opened and is currently
being used by the applications, TRADUMP makes it a lot easier to realize
that the wrong configuration file is being referenced.
Often, when a shared RAM dump is analyzed, you find that the adapter
isn't operating exactly as expected. A SAP that should be opened isn't
there, or maybe a SAP that shouldn't be opened is there. Perhaps a
destination address in a link station control block isn't the correct
one, or a Token-Ring Network adapter has been configured for 8K of
shared RAM, rather than 64K with 16K paging. (This has been known to
happen occasionally when a PS/2 Reference Diskette is used to auto-
configure a system with a Token-Ring Network adapter.) These types of
things aren't readily apparent when looking at configuration files, and
TRADUMP may actually lead you to a mis-configured parameter in a place
you wouldn't have thought of looking before.
INSUFFICIENT RESOURCES
Each LAN application has different requirements in terms of LAN
resources. Sometimes these requirements are not spelled out adequately
in the application documentation, or the documentation is incorrect.
TRADUMP can show very clearly what adapter resources an application has
allocated, and how it is using the resources.
VERIFYING CONNECTIONS
Some PS/2's such as servers and gateways may connect to a large number
of other devices on the LAN. Although the server and gateway
applications themselves have utilities to display or list connected
devices, the information is usually at a high level. TRADUMP can
supplement this connectivity status by providing details about the link
connection between the systems (including error counts, MAC addresses,
timer values, and bridge path).
SOFTWARE DEFECTS
TRADUMP can be useful in disclosing a logic error in a software
component, in terms of its use of the LAN adapter. This software might
either be a part of OS/2 or one of its subsystems, or an application
program written to the 802.2 API. On one occasion, changing MAXOUT and
MAXIN on an application configuration panel for the purpose of improving
performance actually degraded performance drastically. By looking at
the link station control block, it turned out that while MAXIN had been
changed to the expected value, MAXOUT had not changed. With MAXIN on
one system exceeding MAXOUT on the partner system, a significant delay
was encountered every time a frame was sent, because the acknowledgement
didn't flow until the receiver acknowledgement timer (T2) expired. A
simple correction to the logic of the 802.2 application corrected the
problem.
TRADUMP AND SNAPDUMP/2
TRADUMP may be run on-demand as a standalone tool, even remotely.
However, its greatest potential is realized when the dump is analyzed in
conjunction with other detailed information about the system.
SnapDump/2 is a problem management tool that makes it easy to collect
vital problem data from an OS/2 system. It takes a "snapshot" of the
system, gathering a predefined list of files (e.g., IBMLAN.INI,
STARTUP.CMD, Communications Manager configuration file) and executing
status commands (e.g., NET ERROR, SYSLEVEL, PSTAT, NetBIOS resource and
session status, and TRADUMP). All of this information is consolidated
into a single file, which can be shipped to a central site for problem
analysis by skilled personnel.
The format of the command to gather the data is:
SNAPDUMP d:\path\file.in d:\path\file.out
The value "file.in" is the name of the SnapDump/2 input file, a
"shopping list" designating the information that is vital for solving a
particular class of problem. For example, the input file for gathering
the information described above would look like this:
f/IBMLAN.INI
f/STARTUP.CMD
f/*.CFG
p/NET ERROR /R
p/SYSLEVEL
p/PSTAT
p/NCBSTAT *
p/NETSESS2
p/TRADUMP
SnapDump/2 will search all directories for the files designated by "f/" and
copy any occurrences of the files to the SnapDump/2 output file ("file.out").
The commands indicated by "p/" will be executed, with STDOUT redirected to
"file.out". Notice that the TRADUMP command needs no other redirection in
this case, since SnapDump/2 automatically redirects STDOUT to its output file.
In order for TRADUMP to run successfully, it must have been previously
installed on the system, as described in "Installing TRADUMP".
The SnapDump/2 output file can then be viewed by the SNAPDF program,
which is a Presentation Manager (PM) application:
SNAPDF d:\path\file.out
SAMPLE TRADUMP OUTPUT
Return code from TRADUMP.SYS 0
TR adapter type MARS
Adapter supports total SRAM 64 (K)
Page size 16 (K)
Adapter paging supported SRAM paging with 16K page.
Formatting of MMIO Attachment Control Area
SRAM low real address 0D0000
Write window offset 00EEAE
End write window offset 00F640
Write region offset 00F646
SRAM high real address 0D4000
Other control registers available in MMIO - ACA dump.
Dump of MMIO - ACA
1E00 D004F646 EEAEF640 C2000300 E840010A ...F...@.....@..
1E10 00000000 00000000 00000000 00000000 ................
1E20 D004F646 EEAEF640 C2000300 E840010A ...F...@.....@..
1E30 00000000 00000000 00000000 00000000 ................
1E40 D004F646 EEAEF640 C2000300 E840010A ...F...@.....@..
1E50 00000000 00000000 00000000 00000000 ................
1E60 D004F646 EEAEF640 C2000300 E840010A ...F...@.....@..
1E70 00000000 00000000 00000000 00000000 ................
Formatting of MMIO Adapter Identification PROM
Adapter encoded address 10005A8DA203
Signature (channel ident) MARS63X4518
Adapter type 0E
Data rate 16/4 Mbps
Early token release 16 Mbps
Total shared ram 64 KB (top 512 reserved)
Shared ram paging 16 KB page
Max DHB at 4 Mbps 4464 bytes
Max DHB at 16 Mbps 17960 bytes
Other PROM values available in MMIO - AIP dump.
Dump of MMIO - AIP
1F00 01000000 00000000 05000A00 08000D00 ................
1F10 0A000200 00000300 0E000F00 0F000F00 ................
1F20 0A000500 07000200 05000D00 0F000C00 ................
1F30 04000D00 04000100 05000200 05000300 ................
1F40 03000600 03000300 05000800 03000400 ................
1F50 03000500 03000100 03000800 02000000 ................
1F60 0B000F00 0F000F00 0F000F00 0F000F00 ................
1F70 0F000F00 0F000F00 0F000F00 0F000F00 ................
1F80 01000300 05000700 09000B00 0D000F00 ................
1F90 0E000C00 0A000800 06000400 00000200 ................
1FA0 0E000D00 0D000B00 0E000D00 0B000F00 ................
1FB0 0F000F00 0F000F00 0F000F00 0F000F00 ................
1FC0 0F000F00 0F000F00 0F000F00 0F000F00 ................
1FD0 0F000F00 0F000F00 0F000F00 0F000F00 ................
1FE0 0F000F00 0F000F00 0F000F00 0F000F00 ................
1FF0 0F000F00 0F000F00 0F000F00 0F000F00 ................
Formatting of SRAM Node Control Block
Universal address 10005A8DA203
Local administered address 10005A8DA203
End of ram FE00
SRB address FDD8
Adapter open options 2000
Group address 00000000
Functional address 00000080
Minimum receive buffers 002F
Receive buffer length 0060
DHB length 0798
Number of DHBs 02
Maximum # SAPs 05
Maximum # link stations 20
Maximum # group SAPs 00
Maximum members/group SAP 00
Product ID 85654533712121 (ASCII)
T1 timer Group 1 0F
T2 timer Group 1 03
Ti timer Group 1 FF
T1 timer Group 2 19
T2 timer Group 2 0A
Ti timer Group 2 FF
Formatting of SAP and Link Station Control Blocks
Free SAPCB queue DBE8
Free SAPCB count 03
SAPCB base address DB28
Free LSCB queue DEE8
Free LSCB count 14
LSCB base address DC18
Format of SAP for station ids 01xx - value 04 - SNA
Default T1/T2/Ti values 05020A
Default MAXOUT 02
Default MAXIN 01
Default MAXIN/OUT incremnt 01
Default max retries 08
Default max I-field length 0409
LSCBs avail (not in use) 03
Format of LSCB for station id 0101
MAC hdr - Destination addr 400020200212
MAC hdr - Source addr 90005A8DA203
Routing information length 08
MAC hdr - Routing control 0820
MAC hdr - Route segment C0D1
MAC hdr - Route segment B001
MAC hdr - Route segment C030
LLC hdr - DSAP 04
LLC hdr - SSAP 04
LLC hdr - Control field 01A9 (Supervisory, RR)
I-frames transmitted 019D
I-frames received 0154
I-frame transmit errors 00
I-frame receive errors 00
T1 expirations 001A
Last received cmd or rsp 01 (Supervisory, RR)
T1/T2/Ti values 05020A
Link primary state 01 (Open)
Link secondary state 00
Vs - send state 3A
Vr - receive state A8
Va - acknowledge state 3A
Vi - initialization state 00
TW - max transmit window 07
N3 - I-fmt LPDUs betw acks 01
Nw - I-fmt LPDUs ack to Ww 01
N2 - retries allowed 08
N1 - max length I-field 0409
Is_Ct - I-fmt retry count 08
P_Ct - Poll retry count 08
Ww - working window size 07
Working MAXIN 01
Ia_Ct - I-fmt LPDUs acked 00
Format of SAP for station ids 02xx - value F0 - NETBIOS
Default T1/T2/Ti values 050203
Default MAXOUT 02
Default MAXIN 01
Default MAXIN/OUT incremnt 01
Default max retries 08
Default max I-field length 1170
LSCBs avail (not in use) 05
Format of LSCB for station id 0202
MAC hdr - Destination addr 10005A8DAA7C
MAC hdr - Source addr 90005A8DA203
Routing information length 06
MAC hdr - Routing control 06B0
MAC hdr - Route segment 0891
MAC hdr - Route segment C0D0
LLC hdr - DSAP F0
LLC hdr - SSAP F1
LLC hdr - Control field 0146 (Supervisory, RR)
I-frames transmitted 0027
I-frames received 0023
I-frame transmit errors 00
I-frame receive errors 00
T1 expirations 0000
Last received cmd or rsp 44 (I-frame)
T1/T2/Ti values 060304
Link primary state 01 (Open)
Link secondary state 00
Vs - send state 4E
Vr - receive state 46
Va - acknowledge state 4E
Vi - initialization state 00
TW - max transmit window 02
N3 - I-fmt LPDUs betw acks 01
Nw - I-fmt LPDUs ack to Ww 01
N2 - retries allowed 08
N1 - max length I-field 1170
Is_Ct - I-fmt retry count 08
P_Ct - Poll retry count 08
Ww - working window size 02
Working MAXIN 01
Ia_Ct - I-fmt LPDUs acked 00
Format of LSCB for station id 0203
MAC hdr - Destination addr 10005A8DFC27
MAC hdr - Source addr 90005A8DA203
Routing information length 06
MAC hdr - Routing control 06B0
MAC hdr - Route segment 0891
MAC hdr - Route segment C0D0
LLC hdr - DSAP F0
LLC hdr - SSAP F1
LLC hdr - Control field 0113 (Supervisory, RR)
I-frames transmitted 0011
I-frames received 0009
I-frame transmit errors 00
I-frame receive errors 00
T1 expirations 0000
Last received cmd or rsp 01 (Supervisory, RR)
T1/T2/Ti values 060304
Link primary state 01 (Open)
Link secondary state 00
Vs - send state 22
Vr - receive state 12
Va - acknowledge state 22
Vi - initialization state 00
TW - max transmit window 02
N3 - I-fmt LPDUs betw acks 01
Nw - I-fmt LPDUs ack to Ww 01
N2 - retries allowed 08
N1 - max length I-field 1170
Is_Ct - I-fmt retry count 08
P_Ct - Poll retry count 08
Ww - working window size 02
Working MAXIN 01
Ia_Ct - I-fmt LPDUs acked 00
Format of LSCB for station id 0204
MAC hdr - Destination addr 10005A8DF8A6
MAC hdr - Source addr 90005A8DA203
Routing information length 06
MAC hdr - Routing control 06B0
MAC hdr - Route segment 0891
MAC hdr - Route segment C0D0
LLC hdr - DSAP F0
LLC hdr - SSAP F1
LLC hdr - Control field 0108 (Supervisory, RR)
I-frames transmitted 0005
I-frames received 0004
I-frame transmit errors 00
I-frame receive errors 00
T1 expirations 0000
Last received cmd or rsp 06 (I-frame)
T1/T2/Ti values 060304
Link primary state 01 (Open)
Link secondary state 00
Vs - send state 0A
Vr - receive state 08
Va - acknowledge state 0A
Vi - initialization state 00
TW - max transmit window 02
N3 - I-fmt LPDUs betw acks 01
Nw - I-fmt LPDUs ack to Ww 01
N2 - retries allowed 08
N1 - max length I-field 1170
Is_Ct - I-fmt retry count 08
P_Ct - Poll retry count 08
Ww - working window size 02
Working MAXIN 01
Ia_Ct - I-fmt LPDUs acked 00
SAP for station ids 03xx at DBE8 is not open.
SAP for station ids 04xx at DC28 is not open.
SAP for station ids 05xx at DC68 is not open.
LSCB for station id xx05 at DEE8 is unused.
LSCB for station id xx06 at DF78 is unused.
LSCB for station id xx07 at E008 is unused.
LSCB for station id xx08 at E098 is unused.
LSCB for station id xx09 at E128 is unused.
.
.
.
LSCB for station id xx10 at E518 is unused.
LSCB for station id xx11 at E5A8 is unused.
LSCB for station id xx12 at E638 is unused.
LSCB for station id xx13 at E6C8 is unused.
LSCB for station id xx14 at E758 is unused.
LSCB for station id xx15 at E7E8 is unused.
LSCB for station id xx16 at E878 is unused.
LSCB for station id xx17 at E908 is unused.
LSCB for station id xx18 at E998 is unused.
LSCB for station id xx19 at EA28 is unused.
LSCB for station id xx1A at EAB8 is unused.
LSCB for station id xx1B at EB48 is unused.
LSCB for station id xx1C at EBD8 is unused.
LSCB for station id xx1D at EC68 is unused.
LSCB for station id xx1E at ECF8 is unused.
LSCB for station id xx1F at ED88 is unused.
LSCB for station id xx20 at EE18 is unused.
INTRODUCTION TO INSTALLING AND USING
LAN ADAPTER AND PROTOCOL SUPPORT DUMP/FORMATTER (LAPSDUMP)
May 19, 1992
Mark B. Arslan (ARSLAN @ DALVM41B)
Systems/Networking Management Services
Networking & Systems Services & Support
Cary, NC
(i)
NOTICES
The information contained in this document has not been submitted to any
formal IBM test and is distributed on an "as-is" basis without any
warranty either expressed or implied. The use of this information or
the implementation of any of these techniques is a customer
responsibility and depends on the customer's ability to evaluate and
integrate them into the customer's operational environment. While each
item may have been reviewed by IBM for accuracy in a specific situation,
there is no guarantee that the same or similar results will be obtained
elsewhere. Customers attempting to adapt these techniques to their own
environments do so at their own risk.
Performance data contained in this document was determined in a
controlled environment; and therefore, the results which may be obtained
in other operating environments may vary significantly. Users of this
document should verify the applicable data for their specific
environment.
References in this publication to IBM products, programs, or services do
not imply that IBM intends to make these available in all countries in
which IBM operates. Any reference to an IBM licensed program in this
publication is not intended to state or imply that only IBM's program
may be used. Any functionally equivalent program may be used instead.
(ii)
PREFACE
In the complex area of distributed OS/2 local area networks, one of the
most important elements of problem management is problem source
identification. It is the process of isolating a problem to its failing
component or the system resource responsible for the problem. Problem
source identification (or PSI) is particularly difficult in this
environment due to the large number of interrelated system components
and the relative scarcity of adequate PSI facilities (tools, utilities,
product functions) and documented PSI procedures.
A class of LAN problems that can be especially challenging is that of
LAN connectivity ("System A can't communicate with System B over the
network"). Solving this type of problem often requires knowledge of the
workings of the layers of the protocol stack (802.5, 802.2, NetBIOS,
SNA, etc.) on each system, including APIs, resource requirements,
contents of internal buffers, event logs, messages, and formats and
protocols of frame exchange. When connectivity problems occur, clues
are often left behind. Analyzing these elements of the protocol layers
will usually lead to the solution of the problem, provided that the
problem-solver has adequate tools and sufficient skills.
Some particularly useful components for PSI include the following:
- Shared RAM and memory-mapped I/O (MMIO) in the IBM PS/2 Token-Ring
Network adapter
- Work area of the 802.2 protocol driver (LANDD.OS2)
- Work areas of the NetBIOS protocol driver (NETBEUI.OS2) and device
driver for API support (NETBIOS.OS2)
There is a tool called LAPSDUMP that dumps these buffer areas and
formats the dump data into an ASCII text file or STDOUT. The purpose of
this manual is to show technically-knowledgeable SEs and specialists how
to use LAPSDUMP effectively (in conjunction with other tools and
facilities) to aid in the resolution of LAN connectivity problems.
Note: The supported adapters for the shared RAM and MMIO dumps include
the IBM Token-Ring Network adapters that operate as described in Chapter
7 of the IBM LOCAL AREA NETWORK TECHNICAL REFERENCE (SC30-3383-03).
This does not include the IBM Token-Ring Network Busmaster Server
Adapter/A. However, the 802.2 and NetBIOS protocol drivers can be
dumped regardless of the type of LAN adapters present.
LAN Adapter and Protocol Support (LAPS) ships with Extended Services for
OS/2 and LAN Server V2.0. LAPS handles shared RAM and the NetBIOS/802.2
interface quite differently than OS/2 Extended Edition V1.3. Under OS/2
EE V1.3, a dump of MMIO and shared RAM is provided by a tool called
Token-Ring Network Adapter Shared RAM Dump (TRADUMP). Refer to the
manual GUIDELINES FOR USING TRADUMP FOR DEBUGGING LAN CONNECTIVITY
PROBLEMS (GG66-3227).
(iii)
RELATED PUBLICATIONS
A much more detailed discussion of interpreting LAPSDUMP output can be
found in :
GUIDELINES FOR USING LAN ADAPTER & PROTOCOL SUPPORT DUMP/FORMATTER
(LAPSDUMP) FOR DEBUGGING LAN CONNECTIVITY PROBLEMS
No form number has been assigned yet, but a copy of this document may be
obtained by having your Systems Engineer contact this author (ARSLAN @
DALVM41B).
The following publications contain information that may also be helpful:
IBM LOCAL AREA NETWORK TECHNICAL REFERENCE (SC30-3383-03)
IBM TOKEN-RING NETWORK ARCHITECTURE REFERENCE (SC30-3374-02)
IBM NDIS IMPLEMENTATION INFORMATION: IBM OS2 LAN TECHNICAL REFERENCE
EXTENSIONS, dated March 3, 1992, available from IBM Corporation, PS
Programming Center, 11400 Burnet Road, Austin, TX 78758.
IBM OS/2 LAN SERVER V2.0 NETWORK ADMINISTRATOR REFERENCE, Volume 2:
Performance Tuning (S04G-1033)
(1)
INSTALLING LAPSDUMP
LAPSDUMP consists of two modules:
LAPSDUMP.EXE
A program that obtains the work areas from LANDD.0S2, NETBEUI.OS2, and
NETBIOS.OS2, and the TRADUMP.SYS program buffer, formats the raw data,
and writes the formatted dump to STDOUT (i.e., text mode standard output
to the PS/2 screen).
TRADUMP.SYS
A device driver that determines the location of MMIO and shared RAM in
the PS/2 memory address space, reads the contents of each, and writes
the output to a program buffer.
To install LAPSDUMP, perform the following steps:
1. Copy both TRADUMP.SYS and LAPSDUMP.EXE to the local fixed disk. A
recommended approach is to copy LAPSDUMP.EXE into a directory that is
pointed to by the PATH statement in CONFIG.SYS. (Another alternative is
to put LAPSDUMP.EXE on a diskette or redirected drive. TRADUMP.SYS must
be on a local disk, since it is a device driver.)
2. Add a statement to CONFIG.SYS to load the TRADUMP.SYS device driver
at IPL time:
DEVICE=d:\path\TRADUMP.SYS
3. Re-IPL the system to allow this change to CONFIG.SYS to take effect.
Note: TRADUMP.SYS is optional, if you don't require the information
provided by shared RAM and MMIO. LAPSDUMP will bypass the formatting of
those areas if it detects that TRADUMP.SYS has not been loaded.
(2)
RUNNING LAPSDUMP
LAPSDUMP can be run by issuing the LAPSDUMP command at an OS/2 command
prompt. This command requires no additional user interaction, and
writes to STDOUT, so it can be entered manually by an operator, called
by another program (e.g., SnapDump/2), or issued remotely from a product
like LAN Management Utilities/2 (LMU/2) or Distributed Console Access
Facility (DCAF).
COMMAND FORMAT
The format of the LAPSDUMP command is as follows:
------.----------.---.----------.---- LAPSDUMP ----->
|--drive---| |---path---|
---.-------------------------------------.-------Ü
|----------------- ? -----------------|
| .-------------------------. |
|-----V---√-----------------√---|-----|
°- /f<m,s,l,n,y> -Ü
°-- /a<0|1|2|3> --Ü
ⁿ------ /d -------α
LAPSDUMP extracts memory segments from the LAN Adapter & Protocol Support
(LAPS) modules in OS/2, and format/dumps that memory. It also uses the
TRADUMP.SYS device driver (if present) to format/dump the contents of the
token ring adapter shared ram memory and/or the MMIO region.
The /f option chooses the memory to format. Any combination of the choices
<m,s,l,n,y> is allowed (no intervening blanks). The default is to format all.
/fm format the MMIO region at 0x1E00(256) and 0x1F00(512).
/fs format control blocks from the adapter SRAM memory.
/fl format the LANDD (802.2) memory segments.
/fn format the NETBEUI/NETBIOS memory segments.
/fy format only the NETBIOS memory segment.
/a specifies primary (0) or an alternate (1|2|3) adapter.
/d in addition to formatting, dump the specified memory areas.
Note: TRADUMP.SYS is only needed for the /fms memory options.
To display this format diagram, key "LAPSDUMP ?".
(3)
OPTIONS
"/f" (areas to format)
LAPSDUMP can dump and format several different areas of memory, either
separately, or as a whole. The "/f" option allows you to specify which
area(s) you are interested in.
To dump all areas, key "LAPSDUMP /fsmlny", "LAPSDUMP /f", or just plain
"LAPSDUMP". The default is to dump and format all areas.
To dump only a particular area, or areas, include the desired value(s)
after the "/f" option. For example, to dump only the work area of the
802.2 protocol driver (LANDD.OS2), key "LAPSDUMP /fl". To dump both
802.2 and NetBIOS, key "LAPSDUMP /fln".
The value "n" includes the work areas of both the NetBIOS protocol
driver (NETBEUI.OS2) and device driver for API support (NETBIOS.OS2).
NETBIOS.OS2's work area describes the "ring 3" NetBIOS applications.
The "y" option is used to dump only the NETBIOS.OS2 work area. (That
is, "y" is a subset of the "n" option.) To gather information about the
resource allocation and usage of ring 3 NetBIOS applications only, key
"LAPSDUMP /fy".
"/a" (adapter number)
For the dump of shared RAM and/or MMIO, the "/a" option refers to the
physical number of the adapter being dumped, since these areas reside on
the adapter itself. A value of "0" (the default) refers to the primary
Token-Ring Network adapter, while a "1" refers to the alternate adapter.
For example, the command "LAPSDUMP /fsm /a1" will dump and format the
shared RAM and MMIO for the alternate Token-Ring Network adapter. Values
of "2" or "3" have no meaning in this context and should not be used.
For the remaining areas to be dumped (802.2 and NetBIOS), the "/a"
option refers to the logical, not physical, adapter number that was
configured for the 802.2 and NetBIOS protocol drivers. For example, the
command "LAPSDUMP /fln /a3" will dump the 802.2 and NetBIOS information
corresponding to logical adapter number 3 (which is, in turn, bound to a
network adapter (MAC) driver).
If the PS/2 has only a single Token-Ring Network adapter configured as
primary, and the 802.2 and NetBIOS protocol drivers are both configured
with logical adapter number 0, then it is not necessary to code the "/a"
option in the command.
(4)
"/d" (unformatted dump)
The "/d" option will create an unformatted hexadecimal dump of the
control blocks from each of the areas that are selected to be dumped.
Among other things, this can be used to present the data in the transmit
and receive buffers (although the boundaries between the various buffers
and control blocks are not shown, making it difficult to interpret).
This option was intended for use by IBM support personnel.
The options (/f, /a, and /d) and the values (m, s, l, n, and y) can be
entered in either upper or lower case. The value must immediately
follow the option, with no blank separating them. If multiple options
are entered, such as "LAPSDUMP /fy /a1", a blank must separate the first
option-value from the second. "LAPSDUMP /fy/a1" will result in an
error.
Since LAPSDUMP.EXE writes to STDOUT, the dump will scroll up the PS/2
screen. While this is necessary for use in certain products like
SnapDump/2, a more desirable approach may be to redirect STDOUT to
either a printer or a disk file, or pipe it to MORE.
LAPSDUMP >lpt1:
or
LAPSDUMP >g:\dumps\srammmio.dmp
or
LAPSDUMP |MORE
The resulting ASCII text file may then be shipped to a central site
for analysis, where it can be viewed with a standard text editor by
technical support personnel.
(5)
ERRORS
LAPSDUMP calls TRADUMP.SYS, LANDD.OS2, and NETBEUI.OS2 to access the
requested information. If it is unable to successfully obtain the
information from any of these modules, an error message will be sent to
STDOUT (along with the rest of the formatted output).
TRADUMP.SYS
The following message indicates that the TRADUMP.SYS device driver has
not been loaded. Check CONFIG.SYS to make sure that a
DEVICE=\path\TRADUMP.SYS statement is present.
Error on DosOpen for TRADUMP device driver, rc = 110
rc 110 indicates that TRADUMP.SYS is not installed.
If TRADUMP.SYS detects an error that prevents it from dumping Token-Ring
Network adapter memory correctly, one of the following return codes will
be displayed:
rc=3
TRADUMP.SYS issued a programmed I/O (PIO) read to the port for the
indicated adapter, and invalid information was returned. Check that the
adapter specification on the LAPSDUMP command is correct (/a0 or default
for the primary adapter, /a1 for the alternate adapter), and that the
particular adapter is actually installed and configured.
rc=4
The specified adapter is not one that is understood by this program.
Check that the adapter being dumped is supported by LAPSDUMP.
rc=5
The specified adapter indicates that it uses a paging method that is not
understood by this program.
For RC= 4 or 5, the MMIO area of the adapter memory is automatically
dumped for analysis. Have this information available when reporting
this as a problem.
A return code of 0 indicates successful completion of the shared RAM or
MMIO dump.
(6)
LANDD.OS2 and NETBEUI.OS2
If LAPSDUMP is not able to access these protocol drivers, then one or
both of the following messages will appear:
Error 3 on Open of \dev\landd$ for V2 DD dump.
Error 3 on Open of \dev\netbeui$ for V2 DD dump.
If this occurs, check the CONFIG.SYS file to make sure that the DEVICE=
statements reference these drivers. Also, check LANTRAN.LOG for any
indications that they didn't load properly. (If you have replaced these
drivers with other 802.2 or NetBIOS protocol drivers, then LAPSDUMP may
not function properly.)
(7)
PERFORMANCE
LAPSDUMP was designed to run on an active system without interrupting
normal operations. TRADUMP.SYS will extract the MMIO and shared RAM
information from the adapter in a split-second, and write the data to a
program buffer. Once this is done, the adapter is not "touched"
anymore. LAPSDUMP.EXE will then format the data and write it to STDOUT
(i.e., the screen), which could be redirected to a disk file. (The
calls to the LANDD.OS2 and NETBEUI.OS2 protocol drivers are also
designed to be non-disruptive.)
On a PS/2 Model 65SX, this whole operation takes less than three seconds
(most of that time loading LAPSDUMP.EXE from disk, and then writing the
redirected dump back to disk).
Dumping with the "/d" option (unformatted contents of all the control
blocks) takes considerably longer (3 minutes, 20 seconds on a PS/2 Model
65SX). Almost all of that time is spent writing to the disk file.
However, this option is not expected to be used very often.
(8)
SCENARIOS
What kinds of problems can LAPSDUMP be applied to in order to help
identify the problem source? And how can it be used most effectively?
These questions can perhaps best be answered by describing some ways in
which this information has been used by IBM support center personnel to
solve customer problems with LAN connectivity.
CONFIGURATION ERRORS
OS/2 provides the capability of running many LAN applications
concurrently. To do this, the system needs to be configured properly.
Some of these configuration parameters include LAN resources, "pointers"
to other systems (e.g., partner LU definitions, gateway addresses,
server names), and various performance options. The more LAN
applications that are installed on a single system, the more likely a
configuration error is likely to occur, since many of these parameters
are interdependent.
Configuration errors can be hard to track down. With the complexity of
application programs, operating system components, and protocol layers
between the user and the actual cause of the error, it isn't uncommon
for the error message to be less than helpful in resolving the problem.
Sometimes the listings of configuration files provided to the help desk
are either out-of-date, or are of the wrong files.
Often, when a dump is analyzed, you find that the adapter isn't
operating exactly as expected. A SAP that should be opened isn't there,
or maybe a SAP that shouldn't be opened is there. Perhaps a destination
address in an LTE isn't the correct one, or a Token-Ring Network adapter
has been configured for 8K of shared RAM, rather than 64K with 16K
paging. (This has been known to happen occasionally when a PS/2
Reference Diskette is used to auto-configure a system with a Token-Ring
Network adapter.) These types of things aren't readily apparent when
looking at configuration files, and LAPSDUMP may actually lead you to a
mis-configured parameter in a place you wouldn't have thought of looking
before.
INSUFFICIENT RESOURCES
Each LAN application has different requirements in terms of LAN
resources. Sometimes these requirements are not spelled out adequately
in the application documentation, or the documentation is incorrect.
LAPSDUMP can show very clearly what adapter resources an application has
allocated, and how it is using the resources.
(9)
VERIFYING CONNECTIONS
Some PS/2's such as servers and gateways may connect to a large number
of other devices on the LAN. Although the server and gateway
applications themselves have utilities to display or list connected
devices, the information is usually at a high level. LAPSDUMP can
supplement this connectivity status by providing details about the link
connection between the systems (including error and traffic counts,
NetBIOS names, MAC addresses, timer values, and bridge path).
SOFTWARE DEFECTS
LAPSDUMP can be useful in disclosing a logic error in a software
component, in terms of its use of the LAN adapter. This software might
either be a part of OS/2 or one of its subsystems, or a user application
program written to the 802.2 or NetBIOS APIs. On one occasion, changing
MAXOUT and MAXIN on an application configuration panel for the purpose
of improving performance actually degraded performance drastically. By
looking at the LTE, it turned out that while MAXIN had been changed to
the expected value, MAXOUT had not changed. With MAXIN on one system
exceeding MAXOUT on the partner system, a significant delay was
encountered every time a frame was sent, because the acknowledgement
didn't flow until the receiver acknowledgement timer (T2) expired. A
simple correction to the logic of the 802.2 application corrected the
problem.
UNEXPECTED PROBLEMS
In one case, a requester was unable to logon to a server. The server's
logon status utility (NET WHO) showed that the user was already logged
on. A dump of the server's NetBIOS session and link tables showed that
someone was indeed logged on with the same ID as the requester. The
routing information field in the LTE revealed the MAC address and
location (ring) of the "culprit".
(10)
LAPSDUMP and SNAPDUMP/2
LAPSDUMP may be run on-demand as a standalone tool, even remotely.
However, its greatest potential is realized when the dump is analyzed in
conjunction with other detailed information about the system.
SnapDump/2 is a problem management tool that makes it easy to collect
vital problem data from an OS/2 system. It takes a "snapshot" of the
system, gathering a predefined list of files (e.g., IBMLAN.INI,
STARTUP.CMD, Communications Manager configuration file, PROTOCOL.INI)
and executing status commands (e.g., NET ERROR, SYSLEVEL, PSTAT, NetBIOS
resource and session status, and LAPSDUMP). All of this information is
consolidated into a single file, which can be shipped to a central site
for problem analysis by skilled personnel.
The format of the command to gather the data is:
SNAPDUMP d:\path\file.in d:\path\file.out
The value "file.in" is the name of the SnapDump/2 input file, a
"shopping list" designating the information that is vital for solving a
particular class of problem. For example, the input file for gathering
the information described above would look like this:
f/IBMLAN.INI
f/STARTUP.CMD
f/*.CFG
f/PROTOCOL.INI
p/NET ERROR /R
p/SYSLEVEL
p/PSTAT
p/NCBSTAT *
p/NETSESS2
p/LAPSDUMP
SnapDump/2 will search all directories for the files designated by "f/"
and copy any occurrences of the files to the SnapDump/2 output file
("file.out"). The commands indicated by "p/" will be executed, with
STDOUT redirected to "file.out". Notice that the LAPSDUMP command needs
no other redirection in this case, since SnapDump/2 automatically
redirects STDOUT to its output file.
The SnapDump/2 output file can then be viewed by the SNAPDF program,
which is a Presentation Manager (PM) application:
SNAPDF d:\path\file.out
(11)
SAMPLE LAPSDUMP OUTPUT
------------------------------------------------------------
LAN Adapter & Protocol Support Dump/Formatter (LAPSDUMP) - V1.0
------------------------------------------------------------
Initiating adapter memory extraction.
Return code from TRADUMP.SYS 0
TR adapter type MARS
Adapter supports total SRAM 64 (K)
Page size 16 (K)
Adapter paging supported SRAM paging with 16K page.
Format of MMIO Attachment Control Area
SRAM low real address x0D0000
Write window offset x00DAFE
End write window offset x00EC68
Write region offset x00EC6E
SRAM high real address x0D4000
Other control registers available in MMIO - ACA dump.
Dump of MMIO - ACA
1E00 D004EC6E DAFEEC68 C2000700 E840B5FF ...n...h.....@..
1E10 00000000 00000000 C0000000 00000000 ................
1E20 D004EC6E DAFEEC68 C2000700 E840B5FF ...n...h.....@..
1E30 00000000 00000000 C0000000 00000000 ................
1E40 D004EC6E DAFEEC68 C2000700 E840B5FF ...n...h.....@..
1E50 00000000 00000000 C0000000 00000000 ................
1E60 D004EC6E DAFEEC68 C2000700 E840B5FF ...n...h.....@..
1E70 00000000 00000000 C0000000 00000000 ................
Format of MMIO Adapter Identification PROM
Adapter encoded address x10005A8DA203
Signature (channel ident) MARS63X4518
Adapter type x0E
Data rate 16/4 Mbps
Early token release 16 Mbps
Total shared ram 64 KB (top 512 reserved)
Shared ram paging 16 KB page
Max DHB at 4 Mbps 4464 bytes
Max DHB at 16 Mbps 17960 bytes
Other PROM values available in MMIO - AIP dump.
Dump of MMIO - AIP
1F00 01000000 00000000 05000A00 08000D00 ................
1F10 0A000200 00000300 0E000F00 0F000F00 ................
1F20 0A000500 07000200 05000D00 0F000C00 ................
1F30 04000D00 04000100 05000200 05000300 ................
1F40 03000600 03000300 05000800 03000400 ................
1F50 03000500 03000100 03000800 02000000 ................
1F60 0B000F00 0F000F00 0F000F00 0F000F00 ................
1F70 0F000F00 0F000F00 0F000F00 0F000F00 ................
(12)
Dump of MMIO - AIP (continued)
1F80 01000300 05000700 09000B00 0D000F00 ................
1F90 0E000C00 0A000800 06000400 00000200 ................
1FA0 0E000D00 0D000B00 0E000D00 0B000F00 ................
1FB0 0F000F00 0F000F00 0F000F00 0F000F00 ................
1FC0 0F000F00 0F000F00 0F000F00 0F000F00 ................
1FD0 0F000F00 0F000F00 0F000F00 0F000F00 ................
1FE0 0F000F00 0F000F00 0F000F00 0F000F00 ................
1FF0 0F000F00 0F000F00 0F000F00 0F000F00 ................
Format of SRAM Node Control Block
Universal address x10005A8DA203
Local administered address x10005A8DA203
End of ram xFE00
SRB address xFDD8
Adapter open options x2000
Group address x00000000
Functional address x00000080
Minimum receive buffers 2
Receive buffer length 264
DHB length 4464
Number of DHBs 2
Maximum # SAPs 0
Maximum # link stations 0
Maximum # group SAPs 0
Maximum members/group SAP 0
Node Control Block indicates LAN Adapter & Protocol Support in use.
(13)
Initiating LAPS memory extraction.
LANDD memory obtained in 1 segment(s).
Format of LAN Control Block - Adapter 00
MAC address x10005A8DA203
LAN header type x0004 (Token Ring)
Media bandwidth (bits/sec) x003D0900 (4.0 Mbit)
Max frame size (bytes) 4456
Maximum SAPs 4
Open SAPs 1
Maximum links (LTEs) 10
Open links (LTEs) 1
Available links (LTEs) 6
Microcode level x000008C1F7F8F0F6F440
Last reported ring status x0000
Status report period x016C0025 (364 min, 37 sec)
FRMRs received on this LAN 0
FRMRs xmitted on this LAN 0
I-frames received in error 0
I-frames xmitted in error 0
Aborted transmissions 0
Successful packets xmitted 2448
Successful packets received 1102204
Times buffer not available 0
DLC T1 timer expirations 0
DLC Ti timer expirations 426
(14)
Format of active SAPs
SAP for station ids 04xx - value 04 - SNA
Default T1 value x0065 (4.040 seconds)
Default T2 value x0009 (0.360 seconds)
Default Ti value xCC52 (52.306 seconds)
Default MAXOUT 8
Default MAXIN 1
Default MAXIN/OUT incremnt 1
Default max retries 8
Default max I-field length 1929
LTEs avail (not in use) 3
LTEs in use 1
Count of buffers in pool 5
Size of buffers in pool 2032
Frames xmitted 1049
Frames received 1099
Frames discarded 0
No. times data was lost 0
Format of Link Table Entries (LTEs) for this SAP
Station id x0401
MAC hdr - Destination addr x400020200212
MAC hdr - Source addr x90005A8DA203
MAC hdr - Routing control x0820
MAC hdr - Route segment xC0D1
MAC hdr - Route segment xB011
MAC hdr - Route segment xC030
LLC hdr - DSAP x04
LLC hdr - SSAP x05
LLC hdr - Control field x0187 (Supervisory, RR)
I-frames xmitted 1041
I-frames received 1091
I-frame xmit errors 0
I-frame receive errors 0
T1 expirations 0
Last received cmd or rsp x01 (Supervisory, RR)
Last sent cmd or rsp x01 (Supervisory, RR)
T1 value x0065 (4.040 seconds)
T2 value x0009 (0.360 seconds)
Ti value xCC52 (52.306 seconds)
(15)
Format of Link Table Entries (LTEs) for this SAP (continued)
Link state x0001 (Open)
Vs - send state x11
Vr - receive state x43
Va - acknowledge state x11
TW - max xmit window 7
N3 - I-fmt LPDUs betw acks 1
Nw - I-fmt LPDUs ack to Ww 1
N2 - retries allowed 8
N1 - max length I-field 1929
Ww - working window size 7
Working MAXIN 1
Ia_Ct - I-fmt LPDUs acked 0
Format of Application Control Blocks a.k.a. Users
Configured users 4
Free users 3
Active users 1
Application 802.2 id 2
Application key xB3CF
Device driver (name) ACSLDLA$
(16)
NETBEUI memory obtained in 1 segment(s).
Format of LAN Control Block - Adapter 00
MAC address x10005A8DA203
LAN header type x0003 (Token Ring)
Media bandwidth (bits/sec) x003D0900 (4.0 Mbit)
Status report period x01690011 (361 min, 17 sec)
Max frame size (bytes) 4456
FRMRs received on this LAN 0
FRMRs xmitted on this LAN 0
I-frames received in error 0
I-frames xmitted in error 0
Aborted transmissions 0
Successful packets xmitted 5445
Successful packets received 1768617
Times buffer not available 0
DLC T1 timer expirations 0
DLC Ti timer expirations 3030
NCBs for Rcv Bcast Datagram 1
NCBs awaiting processing 0
NCBs awaiting completion 0
NCBs on free queue 81
Names in use 6
(17)
Format of Name Table Entries (NTEs)
NTE name Z
Name uninterpreted x0000000000000000000003A28D5A0010
NTE id number 1 (x01)
NTE use count 0
NTE current state x0002 (Registered)
NTE flags x04 (Name number one)
NCBs for Receive Datagram 0
NCBs for Receive Any 0
NTE name ARSLAN
Name uninterpreted x4152534C414E20202020202020202000
NTE id number 2 (x02)
NTE use count 2
NTE current state x0002 (Registered)
NTE flags x00 (Name is unique)
NCBs for Receive Datagram 1
NCBs for Receive Any 1
NTE name ARSLAN
Name uninterpreted x4152534C414E20202020202020202003
NTE id number 3 (x03)
NTE use count 1
NTE current state x0002 (Registered)
NTE flags x00 (Name is unique)
NTE listen-any STE w/ LSN 5 (x05)
NCBs for Receive Datagram 0
NCBs for Receive Any 0
NTE name DSMDOM13
Name uninterpreted x44534D444F4D31332020202020202000
NTE id number 4 (x04)
NTE use count 0
NTE current state x0002 (Registered)
NTE flags x01 (Name is group name)
NCBs for Receive Datagram 1
NCBs for Receive Any 0
NTE name MARKO DSMDOM13
Name uninterpreted x4D41524B4F20202044534D444F4D3133
NTE id number 5 (x05)
NTE use count 0
NTE current state x0002 (Registered)
NTE flags x00 (Name is unique)
NCBs for Receive Datagram 0
NCBs for Receive Any 0
NTE name MARKO
Name uninterpreted x4D41524B4F2020202020202020202003
NTE id number 6 (x06)
NTE use count 1
NTE current state x0002 (Registered)
NTE flags x00 (Name is unique)
NTE listen-any STE w/ LSN 11 (x0B)
NCBs for Receive Datagram 0
NCBs for Receive Any 0
(18)
Format of Name Cache Entries (NCEs) a.k.a. Remote Name Directory
Configured NCEs 6
Free NCEs 3
Active NCEs 3
NCE name LILSERV
Name uninterpreted x4C494C53455256202020202020202020
MAC hdr - Destination addr x10005A8DF8A6
MAC hdr - Source addr x90005A8DA203
MAC hdr - Routing control x06B0
MAC hdr - Route segment x0890
MAC hdr - Route segment xC0D0
NCE name BIGSERV
Name uninterpreted x42494753455256202020202020202020
MAC hdr - Destination addr x10005A8DFC27
MAC hdr - Source addr x90005A8DA203
MAC hdr - Routing control x06B0
MAC hdr - Route segment x0890
MAC hdr - Route segment xC0D0
NCE name DOM13SRV
Name uninterpreted x444F4D31335352562020202020202020
MAC hdr - Destination addr x10005A8DAA7C
MAC hdr - Source addr x90005A8DA203
MAC hdr - Routing control x06B0
MAC hdr - Route segment x0890
MAC hdr - Route segment xC0D0
(19)
Format of Link Table Entries (LTEs)
MAC hdr - Destination addr x10005A8DF8A6
MAC hdr - Source addr x90005A8DA203
MAC hdr - Routing control x06B0
MAC hdr - Route segment x0890
MAC hdr - Route segment xC0D0
LLC hdr - DSAP xF0
LLC hdr - SSAP xF1
LLC hdr - Control field x0170 (Supervisory, RR)
LTE servicing STE w/ LSN 14 (x0E)
Link state x0004 (Opened)
Next N(S) to assign x54
Next N(R) expected x19
Last ACK received x54
Last ACK generated x19
Send window size 3
Receive window size 3
T1 value (adaptive) x0010 (0.640 seconds)
T2 value (adaptive) x0007 (0.280 seconds)
Ti value (adaptive) x3A98 (15.000 seconds)
Maximum frame size 4456
MAC hdr - Destination addr x10005A8DFC27
MAC hdr - Source addr x90005A8DA203
MAC hdr - Routing control x06B0
MAC hdr - Route segment x0890
MAC hdr - Route segment xC0D0
LLC hdr - DSAP xF0
LLC hdr - SSAP xF1
LLC hdr - Control field x0142 (Supervisory, RR)
LTE servicing STE w/ LSN 13 (x0D)
Link state x0004 (Opened)
Next N(S) to assign x54
Next N(R) expected x61
Last ACK received x54
Last ACK generated x61
Send window size 4
Receive window size 3
T1 value (adaptive) x0010 (0.640 seconds)
T2 value (adaptive) x0007 (0.280 seconds)
Ti value (adaptive) x3A98 (15.000 seconds)
Maximum frame size 4456
(20)
Format of Session Table Entries (STEs)
Local session number (LSN) 5 (x05)
Local name ARSLAN
Local name uninterpreted x4152534C414E20202020202020202003
Remote session number (RSN) 0 (x00)
Remote name *
Remote name uninterpreted x2A202020202020202020202020202020
STE serviced by See NTEs
Session state x0002 (Listening)
Xmit correlator x0000
NCBs for Xmits 0
NCBs for Receives 0
NCBs for Gather Send 0
NCBs sent, awaiting ACK 0
Local session number (LSN) 11 (x0B)
Local name MARKO
Local name uninterpreted x4D41524B4F2020202020202020202003
Remote session number (RSN) 0 (x00)
Remote name *
Remote name uninterpreted x2A202020202020202020202020202020
STE serviced by See NTEs
Session state x0002 (Listening)
Xmit correlator x0000
NCBs for Xmits 0
NCBs for Receives 0
NCBs for Gather Send 0
NCBs sent, awaiting ACK 0
Local session number (LSN) 13 (x0D)
Local name ARSLAN
Local name uninterpreted x4152534C414E20202020202020202000
Remote session number (RSN) 195 (xC3)
Remote name BIGSERV
Remote name uninterpreted x42494753455256202020202020202020
STE serviced by LTE to 10005A8DFC27
Session state x0005 (Session established)
Xmit correlator x5BCB
NCBs for Xmits 0
NCBs for Receives 0
NCBs for Gather Send 0
NCBs sent, awaiting ACK 0
Local session number (LSN) 14 (x0E)
Local name ARSLAN
Local name uninterpreted x4152534C414E20202020202020202000
Remote session number (RSN) 248 (xF8)
Remote name LILSERV
Remote name uninterpreted x4C494C53455256202020202020202020
STE serviced by LTE to 10005A8DF8A6
Session state x0005 (Session established)
Xmit correlator xD5A5
NCBs for Xmits 0
NCBs for Receives 0
NCBs for Gather Send 0
NCBs sent, awaiting ACK 0
(21)
NETBEUI summary section
Configured NCBs 85
Unused NCBs 81
Configured sessions 40
Unused sessions 36
Configured names 32
Unused names 26
Configured links 40
Unused links 38
Default T1 value x0010 (0.640 seconds)
Default T2 value x0007 (0.280 seconds)
Default Ti value x3A98 (15.000 seconds)
Max session packet size 4168
Max datagram packet size 512
NETBIOS memory segment obtained. Formatting follows.
Format of NETBIOS Ring 3 users
NETBIOS Ring 3 Users Summary
Maximum sessions available 8
User sessions allocated 0
User sessions in use 0
Maximum commands available 35
User commands allocated 0
User commands in use 0
Maximum names available 18
User names allocated 0
User names in use 0